Printer output can be routed to system or local, ports (see Programming Printer Ports).
NOTES:
We recommend that you print to LPR1 and then, direct LPR1 to a file or Serial port.
You cannot print SIP trunk traffic reports. You can view SIP trunk traffic reports using the SIP TRAFFIC maintenance commands.
Select the traffic reporting options. The parameters in the first part of the form affect the controlling of the traffic session and the formatting of traffic reports. The second part of the Traffic Report Options form provides a list of sections available in the Traffic Reporting feature.
Traffic Report Options Form |
|
Option |
Value |
Time Slot 1 Active (Yes/No) |
|
Start Time 1 (HH::mm: or blank) |
|
Stop Time 1 (HH:mm: or blank) |
|
Time Slot 2 Active (Yes/No) |
|
Start Time 2 (HH::mm: or blank) |
|
Stop Time 2 (HH:mm: or blank) |
|
Time Slot 3 Active (Yes/No) |
|
Start Time 3 (HH::mm: or blank) |
|
Stop Time 3 (HH:mm: or blank) |
|
Time Slot 4 Active (Yes/No) |
|
Start Time 4 (HH::mm: or blank) |
|
Stop Time 4 (HH:mm: or blank) |
|
Time Slot 5 Active (Yes/No) |
|
Start Time 5 (HH::mm: or blank) |
|
Stop Time 5 (HH:mm: or blank) |
|
Time Slot 6 Active (Yes/No) |
|
Start Time 6 (HH::mm: or blank) |
|
Stop Time 6 (HH:mm: or blank) |
|
Period Length (15, or 30, or 60 minutes) |
|
Usage Units (Erlangs or CCS) |
|
Autoprint (Yes/No) |
|
Maximum Number of Traffic Files (0 to 10) |
|
Sections to be included in traffic report |
Yes/No |
Route Plans |
|
Route Lists |
|
Routes |
|
Trunk Groups |
|
Trunks |
|
Links |
|
Group of Links |
|
Channels |
|
DTMF Receivers |
|
Attendants Groups |
|
Attendant Consoles |
|
Attendants |
|
Traffic Options - Definitions |
|
Parameter |
Definition |
Time Slot Active |
This field offers the user the flexibility of collecting traffic reports only during peak hours by initiating reports on a time-slot basis. Users may activate as many as six time slots, providing there is no overlapping time selected. The system checks for overlapped time only on active time slots, which means that overlapping time slots may be programmed as long as they are not active at the same time. Activating a time slot automatically enables the system to collect the SIP trunk traffic data. Traffic reporting stops when changes are made in the programming traffic form or for the system as a whole (e.g. - time change). No traffic report will be generated for the traffic time slot running at the time of the change(s). |
Start Time |
This field indicates the time (in a 24 hour format) when the traffic session will start. If Time Slot Active is changed to Yes values must be specified for Start Time. |
Stop Time |
This entry defines the end of the time slot. If the Stop Time entered is the same as the start time, a 24 hour report will result. When Stop Times do not occur at the same time as the end of a traffic period, a traffic report is generated on the period from the last traffic report to the Stop Time. |
Start/Stop Rules |
Both the Start and Stop Time for an activated time slot must be filled in to be able to commit (will not commit only one field). If the Start or Stop Times are deleted, the Time Slot has to be deactivated before the changes will be accepted. If both times are deleted, the Time Slot, if active, will be set to inactive. |
Period Length |
The accepted values for this field are 15, 30, and 60 minutes. This value defines the duration, in minutes, of the time interval of the traffic data collection. |
Usage Units |
This field selects the usage figures in the report to be printed in Erlangs or CCS. |
Autoprint |
If this option is selected, the traffic files are automatically printed after being formatted. The printer used must be specified in the System Ports form and the Application Logical Ports form. |
Maximum Number of Traffic Files |
This indicates the maximum number of traffic files to be stored on disk. Values range from 0 to 10. The maximum value of 10 would cover a 2.5-hour measurement interval if a 15-minute period length has been selected. |